Advanced voice and data operations in a dual-mode mobile data communication device

ABSTRACT

A system and method for integrating voice and data operations into a single mobile device capable of simultaneously performing data and voice actions. The mobile device working in a network capable of exchanging both cell phone calls and data items to the mobile device. By wearing an earphone or an ear-bud device the user is capable of dealing with voice conversations while working with data centric information related to the current caller. By providing a data-centric device with voice capabilities there is a new range of features that allow incoming data events to trigger outgoing voice events.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.11/924,295 filed Oct. 25, 2007, which is a Continuation of U.S. patentapplication Ser. No. 10/095,603, now U.S. Pat. No. 7,295,836, filed Mar.11, 2002, which claims priority from and is related to the followingprior application: Advanced Voice and Data Operations in a Dual-ModeMobile Data Communication Device, U.S. Provisional Application No.60/274,508, filed Mar. 9, 2001. These prior applications, includingtheir entire written descriptions and drawing figures, are herebyincorporated into the present application by reference.

FIELD OF THE INVENTION

The present invention relates to methods of integrating voice and dataoperations into a single mobile data communications device that iscapable of supporting both voice and data simultaneously.

BACKGROUND OF THE INVENTION

There are very few systems that have integrated a single mobilecommunications device into one physical unit. Those devices that doexist have not taken a data-centric approach to the problem, they havetaken a voice-centric approach to the problem. What this means is thatany previous integrated device normally started with the voice componentand added on the data component as a separate distinct element. As such,the devices have not offered integration of the voice and datacomponents beyond allowing the user to open an address book and place aphone call to the person specified in the address book entry. Many oftoday's current advanced phones have this simple feature, but none ofthem have examined the problem of integrating voice into a data-centricdevice.

There remains a need for integrated voice and data device that canhandle interaction between voice and data events seamlessly and easilyfor the user. Moreover, there is also a need to allow the user toperform both voice and data actions simultaneously to gain even greateradvantage when doing voice or data actions.

It is, therefore, desirable to provide a dual mode mobile device thatintegrates a voice component into the functionality of the data portion.

SUMMARY OF THE INVENTION

It is an object of the present invention to obviate or mitigate at leastone disadvantage of previous dual mode mobile devices, and the method ofintegrating voice and data functions on them.

The present invention provides advanced data and voice operations in adual mode mobile device. The present invention permits the performanceof address lookups and phone calls based on incoming e-mail messages,calendar appointments, todo list tasks, and other data items. Theinvention includes the ability to perform a lookup of the address bookdata based on incoming caller id and direct inward dialing information.The invention includes the ability to create a memo-pad entry of callerlog of incoming phone calls. The invention includes the ability toperform advanced multi-way conference calls by using a calendar entry orother data item that stores the telephone numbers to be joined in theconference. The invention includes the use of a single message center tokeep track of all incoming data and voice events into a personalactivity log on the device.

In a first aspect, the present invention provides a method forinitiating a telephone call using a dual mode mobile device that hasdata and voice components. The data component of the dual mode mobiledevice stores, retrieves, receives and displays data. The voicecomponent establishes telephone calls. The method includes the steps ofreceiving a data item, identifying a phone number associated with thedata item and then initiating a telephone call to the associated phonenumber.

In an embodiment of this aspect of the present invention the step ofreceiving the data item includes the step of receiving data items from acomputer associated with the mobile device. In alternate embodiments thedata item is one of an email message, a calendar appointment and an itemon a todo list. The step of identifying the phone number optionallyincludes reading a phone number embedded in the data item, oralternatively can include referencing a phone number, associated withidentifying information embedded in the data item, in an address book,that can reside either in the mobile device, or in a computer associatedwith the mobile device.

The step of identifying the phone number can include the step ofselecting a field in the email message, any field may includecross-referencing the selected field with an email address field or aname entry in an address book. Alternatively the step of including mayinclude parsing the selected field to identify a phone number, whereinthe parsing may include mapping alphabetic characters to a phone number.In an embodiment of the present invention, the step of identifyingfurther includes the step of selecting a phone number from a pluralityof numbers associated with the data item. In another embodiment aplurality of numbers are selected, and the initiation of the telephonecall includes the initiation of a conference call. In the aboveembodiments the telephone call can be established using a communicationschannel on a cellular phone network, or it can be established using acommunications channel with a data based network using avoice-over-packet data session.

In a further aspect of the present invention there is provided a methodof presenting caller information on a dual mode mobile device havingdata and voice components. The mobile device has a set of callpreferences and applications, and the data component is for storing,retrieving, receiving, and displaying data. The voice component forreceiving telephone calls. The method comprises receiving a voice callcontaining caller identification information, determining the datacomponent application to launch based on the call preferences andlaunching the determined data component application. In embodiments ofthe present aspect of the invention the set of call preferences mapsdifferent incoming numbers to different applications, or prompts theuser for an application to launch. The applications include at least oneof a calendar, call log, address book and email client. In a subsequentembodiment of the invention the caller identification informationincludes an originating phone number, and may optionally include acaller name. This information is typically provided to the applicationlaunched, and may be supplemented by information in an address bookentry that is associated with the caller identification information. Insome embodiments, the receipt of a call creates a calendar appointment,alternatively the call log records the caller identification informationin an editable format. In alternate embodiments, the address bookpresents the address information associated with the calleridentification information, or creates a new address book entry to storeinformation associated with the caller identification information. In afurther embodiment the email client creates an email message addressedto and address associated with the caller identification information.

A third aspect of the present invention provides a dual mode mobiledevice connected to a data packet network. This device comprises a datacomponent for storing, retrieving, receiving and displaying dataincluding e-mail messages, calendar appointments, address information,for launching applications associated with the data, and for connectingto the data packet network for sending and receiving data, and a voicecomponent, connected to the data component, for receiving callinitiation information, the voice component for initiating and receivingtelephone calls, and caller identification information, and forproviding the received caller identification information to the datacomponent for cross reference to the data. In an embodiment of thisaspect of the present invention the voice component is connected to atelephone network for initiating and receiving telephone calls, wherethe telephone network can be a cellular telephone network. In otherembodiments of the invention the data packet network is a wireless datapacket network, and the voice component can be connected to the datapacket network for receiving and initiating telephone calls using Voiceover Packet data channels. In a further embodiment the data componenthas a preferences table that determines an application to launch uponreceiving caller identification information from the voice component,and the voice component initiates a telephone call upon receiving callinitiation information from the data component. In yet anotherembodiment of the present invention the data component is additionallyfor establishing data communication channels with a computer over thedata network to transfer data.

In an alternate aspect of the present invention there is provided amethod of synchronising data between a computer and mobile device. Thecomputer and mobile device are connected by a wireless network, and areintermittently connected by a physical link. The method comprises thesteps of interrogating the physical link to determine if a connection ispresent, synchronising the data of the computer and the mobile deviceusing the physical link when the physical link is available andsynchronising the data of the computer and the mobile device using thewireless network connection when the physical link is unavailable.

In a further aspect of the invention there is provided a wirelessconnector, operatively connected to a computer having data andassociated with a mobile device, for routing data between the computerand mobile device, to a wireless network for connecting to the mobiledevice associated with the computer, and to a cradle for intermittentlyconnecting to the mobile device. The wireless connector comprises cradleinterrogation means for determining the status of the connection betweenthe cradle and the mobile device, cradle mobile device transfer means,operatively connected to the cradle interrogation means and the cradle,for routing data from the computer to the mobile device through thecradle when the cradle interrogating means indicate that the mobiledevice is connected to the cradle and wireless mobile device transfermeans, operatively connected to the cradle interrogation means and thewireless network, for routing data from the computer to the mobiledevice through the wireless network when the cradle interrogating meansindicate that the mobile device is not connected to the cradle.

Other aspects and features of the present invention will become apparentto those ordinarily skilled in the art upon review of the followingdescription of specific embodiments of the invention in conjunction withthe accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will now be described, by way ofexample only, with reference to the attached Figures, wherein:

FIG. 1 is a system schematic of the voice and data environments in whichthe mobile device is used;

FIG. 2 a is an illustration of a system and method of placing anoutgoing phone call to a number associated with a field in an e-mailmessage;

FIG. 2 b is an illustration of a graphical user interface of a selectionaction menu;

FIG. 2 c is a block diagram of a mobile device;

FIG. 3 is a flow chart illustrating a system and method of placing anoutgoing phone call to a number associated with a field in an e-mailmessage;

FIG. 4 is an illustration of a system and method of placing an outgoingphone call to a number in the body of an email message;

FIG. 5 is a flow chart illustrating a method of initiating an outgoingphone call to a number associated with a field in a data item;

FIG. 6 is an illustration of a method of initiating a conference call tonumbers associated with fields in a data item;

FIG. 7 is an illustration of a method of initiating a conference call tonumbers stored in a calendar appointment;

FIG. 8 is an illustration of a method of initiating a conference call tonumbers stored in a todo list task;

FIG. 9 is a flow chart illustrating a method of initiating a conferencecall by iterating through a plurality of phone numbers associated withthe contents of fields in a data item;

FIG. 10 illustrates a method of managing incoming phone calls usinginformation provided to the data component of the mobile device by thevoice component;

FIG. 11 is a flow chart illustrating a method of processing an incomingtelephone call;

FIG. 12 illustrates a method of creating an address book contactreference based on the caller id information;

FIG. 13 is a flow chart illustrating a method of locating or creating acontact entry based on incoming caller id information;

FIG. 14 illustrates a method of using the data component obtaininformation, associated with caller id information, using the datanetwork;

FIG. 15 a illustrates a method maintaining a unified user interface totrack incoming and outgoing messages and activities; and,

FIG. 15 b is an illustration of another embodiment of 15 a.

DETAILED DESCRIPTION

Generally, the present invention provides a method and system fortransferring instructions (such as telephone call instructions) andinformation between the data and voice components of a dual mode mobiledevice. Additionally, the present invention provides a method and systemfor synchronizing data between a computer and mobile device using acradle when possible, and a wireless data network when necessary.

With reference to FIG. 1 this overview diagram illustrates anenvironment for the invention to operate in. The invention uses a methodof data transfer to send data items from a host system 160 to a mobiledata communication device (mobile device) 100 which is also referred toas a mobile computer or a mobile computing device, over a communicationchannel 130. The same channel is used to exchange data items between awireless connector program 125 and the mobile device 100 in order tointeract with office systems such as message servers 164, e-mailapplications, voice-mail applications 166, intranet data, databaseengines, Customer Reference Management (CRM) data, SAP data and otherforms of information. The mobile device 100 is also capable ofconnecting to a cradle 110, which is connected to a computer 120, toexchange information. The cradle 110 is used to provide a high bandwidthphysically secure connection between mobile device 100 and computer 120.When the cradle 110 is used for data transfer, the mobile device 100 canbe populated with data such as Personal Information Management (PIM)data, that is saved and accumulated in the desktop computer 120 or adata store coupled to the local area network. Another aspect of themobile device 100 is a connection to a wireless network 150 such as acellular-phone network that utilizes protocols such as Time DivisionMultiple Access (TDMA), Code Division Multiple Access (CDMA), GlobalSystem for Mobile Communications (GSM) and General Packet Radio Service(GPRS). The data and voice communication modes are not mutuallyexclusive and may operate simultaneously on the same mobile device.

A method for connecting the data component of dual mode mobile device100 and computer 120 is provided in U.S. patent application Ser. No.09/087,632, titled “System and Method for Pushing Information from aHost System to a Mobile Data Communication Device,” filed on May 29,1998, which is incorporated by reference. By using this previousinvention the dynamic arrival of data items onto the device makesadvanced and integrated control even more important and easy to achieve.This is because this invention discloses a system that mirrors theuser's corporate data environment, and hence all their contact and phoneinformation. As this information gets sent and mailed around thecorporation, it is much easier to act upon it and perform advancedfunctions.

FIG. 1 shows how a network node used for sending data via a wirelessnetwork, herein referred to as wireless connector 125, can be used toprovide a more fully rounded data centric solution. Wireless connector125, which in a presently preferred embodiment is event-driven, canoperate as software running on computer 120 as illustrated in theembodiment of FIG. 1, or it could be another entity at host location160, coupled to a message server and/or voice mail application which inturn is coupled to one or more computers 120 via a corporate LAN. When auser-defined event has occurred, wireless connector 125 transmitsuser-selected data items 205 from the computer 120 to mobile device 100.A non exhaustive list of data items that can be sent to mobile device100 includes e-mail messages, voice-mail indications, calendar events,todo lists, address book entries, work items or other personalinformation (PIM) data. This pushed data can be input by the user, or byanother, and is typically time sensitive data entered into computer 120in advance of the even that triggers wireless connector 125. Wirelessconnector 125 can interface with cradle device 110, over connection 115so that it can detect if the mobile device 100 is in communication withcradle 110. Connection 115 in presently preferred embodiments can be aserial, infra-red (IR), RF or network connection. Cradle 110 provides aphysical link 105 for the mobile computer 100 that allows the user todock the mobile computer 100 when they are in the office. This dockingprocess is one method for exchange bulk personal information, can alsoprovide other information such as security information, which in oneembodiment includes encryption keys. The cradle 110 also informs thewireless connector program 125 when the mobile device 100 is not in thecradle and therefore should be reached by the data-centric wirelessnetwork 145.

In the illustrated embodiment of FIG. 1, the wireless connector 125 iscoupled to an external network 135, directly via physical link 130.Optionally between wireless connector 125 and network 135 there may be aspecial router such as wireless VPN router 170. External network 135could be any range of networks including but not limited to theInternet, a company intranet, an corporate extranet, a private networksuch as that operated by America On Line (“AOL” ®), an X.25 network, orsome other network such as a local area network (LAN) or wide areanetwork (WAN). In a presently preferred embodiment, network 135 iscapable of exchanging information at extremely high rates. Similarly,physical connection 130 could use a range of existing technologiesincluding but not limited to Ethernet, as described in either the IEEE802.3 specification as a 10 Mbps, 100 Mbps, or gigabit system, or any ofthe variety of IEEE 802.11 standards, Cable Modem, DSL, ISDN, FrameRelay or PSTN, running over any number of physical cables such as highcapacity copper cables such as T1 lines or high bandwidth fiber opticcables. One of skill in the art will readily recognize that many othersuch standard and non-standard communication lines can be used withoutdeparting from the scope of the present invention. By coupling network135 to either the wireless connector 125 directly or via the wirelessVPN router 170, another path is established to allow computer 120 toconnect to the mobile device 100 while it is not attached to cradle 110.

The main advantage of using wireless VPN router 170 is that it could bean off-the-shelf component, and could be integrated with wirelessgateway 140. In a presently preferred embodiment, the VPN connectionwould use a TCP/IP based connection to deliver the messages to themobile device 100. In an alternate embodiment, UDP/IP connection can beused. As shown in FIG. 1, many current wireless networks, requirewireless gateway 140 to be present. Wireless gateway 140 acts as acoupler between the Internet 135 and the data-centric wireless network145. Wireless gateway 140 mitigates problems that may arise from packetsize and network speed differences between Internet 135 and thedata-centric wireless network 145. Typically, this is done through theuse of buffers and packet fragmentation. In conjunction with wirelessconnector 125, wireless gateway 140 can provide push support fordynamically sending data to mobile device 100. To implement pushservices wireless gateway 140 performs routing and addressing functions,specifically ensuring that a valid address for mobile device 100 alwaysexists so that wireless connector 125 can locate it and information canbe sent to mobile device 100 at any time. Once data is delivered to thedata-centric wireless network 145, it can be routed to the mobile device100 and received via link 155. Link 155 is typically an RF connection.

In a presently preferred embodiment, wireless connector 125 is acomputer program designed to dynamically encode information (using are-enveloping technique) from the computer 120 for delivery to themobile device 100. This data transfer technique can take place througheither cradle 110, or over data-centric wireless network 145. In analternative embodiment, data sent from the host system to the device 100via the wireless network 145 may be in response to a user-initiatedcommand transmitted from the device for such data transmission to thedevice. In this manner, the data may be “pulled” to the device. In yetanother embodiment, data sent from the host system to the device 100 viathe wireless network 145 may be in response to predetermined timers, orpolling into data store for detecting changes to a data store. If achange is detected and it is determined that change or the new resultingdata is desired at the mobile device, the data is to be sent via network145.

In a presently preferred embodiment data transmission through wirelessnetwork 145 is performed in a secure fashion. During its initializationmobile device 100 can exchange encryption keys (such as symmetricencryption keys) with wireless connector 125. This exchange of keyscannot be performed over an RF connection if the keys are to remainconfidential as the physical RF channel is insecure and would requirenetwork layer encryption which cannot be facilitated without an initialkey exchange. The symmetric key can be used later to encrypt all dataitems being exchanged between the wireless connector 125 and the mobiledevice 100. In an alternate embodiment, in lieu of the initial exchangeof symmetric keys, the mobile device 100 and wireless connector 125provide each other with the public key of an asymmetric key pair, sothat an initialization over an insecure physical channel such as an RFlink can be provided. The wireless connector 125 also has the ability tocompress the information to varying degrees, depending on the type andbandwidth of the connection used. For one skilled in the art it will beclear that wireless connector 125 can connect to a range of devices likevoice-mail systems, home or office alarm systems, motion detectors,Internet web sites, e-mail message stores, and customer databases aswell as other information sources to collect information to push to themobile device 100.

Host location 160 is, in one embodiment, the network protected by atleast the firewall 162, that computer 120 resides on, in the absence ofa networked computer 120, it is computer 120 and all directly attachedperipherals. It is anticipated that a cradle 110 could be connected tocomputer 120 by a network connection through a hub, or other networkingdevice, or that the cradle 110 would be connected to computer 120, byanother computer attached to the network, host location 160. In apreferred embodiment, computer 120 is in a business office or a homeoffice associated with the user of mobile device 100. This officecontains computer 120 which has access to the user's personalinformation manager (PIM) and personal e-mail information along withother data. In alternative embodiments host location 160 could also be aprimary data center, Internet Service Provider (ISP), network carrierdata communication facilities that securely holds user information andfacilitates data and voice communication. In an advanced embodiment theuser has the ability to enable several paths for wireless connector 125to access their personal information and transmit it to mobile device100.

In all cases, the term host system, home system, desktop system andcomputer 120 refers to an information source where wireless connector125 gets information to send to mobile device 100, via a wirelessnetwork. The wireless connector 125 does not necessarily have to beintegrated with the computer 120, but could also be coupled to computer120 via a LAN, WAN, VPN or some other communications method. The hostsystem is most commonly viewed as residing behind a firewall where amyriad of data items are exchanged, such as voice calls, voice mail,e-mail, corporate documents, database files, video conferences and alarge range of other data.

The term wireless network has been used in two contexts (1) thedata-centric wireless network and (2) the voice-centric wirelessnetwork. However in the coming months and years these two networks aremerging into one single network that can support both voice and datacommunications over the same physical network. The newest of thesecombined networks include, but are not limited to CDMA networks GSM andGPRS networks and future so-called third-generation networks like EDGEand UMTS.

Also FIG. 1 presents an illustration of the data exchanges andrelationships between the various components of the system. FIG. 1illustrates how various types of data (such as e-mail messages,summaries of voice mail messages, etc.) are repackaged 215 and sent viathe wireless network to the mobile device 100. This process of sendingpersonal information for the user, combined with the voice component ofthe mobile device creates a unique synergy.

In this illustration computer 120 is coupled to LAN 210. Eachworkstation on LAN 210 has a connection to the network server forwhatever common, shared services might exist. It is well known in theart that the LAN can extend to remote branch offices and other countriesusing Virtual Private Networks (VPNs) and other advanced wide-areanetworking technology. In this context LAN 210 preferably exists behinda firewall 162, no matter how far that extends.

In this illustrative example a wireless connector 125 operates atcomputer 120 or at a network server where data items 205 are received.When wireless connector 125 is configured to reside on a network,wireless connector 125 can monitor the data items 205 for many usersacross several workstations simultaneously. The data items 205 canoriginate from Internet sources 135, from other LAN workstations 210 orfrom external data sources. Data items 205 include: phone calls, e-mail,corporate inventory records, corporate sales projects, corporate salesand marketing forms, company field service records, company calldispatch requests, real-time phone calls, instant messages from instantmessaging gateways, company or home alarm data, motion and videosensors, heart monitors and vital statistic monitors, fluid levels andlarge equipment feedback data. The other product in the computerindustry, which makes the ‘unified data items’ concept shown in FIG. 1easier to understand, is the universal inbox or the unified messagingproduct offerings. There is a new class of software products that arebeing seen as ‘add-ons’ to the desktop, with their sole purpose being tounify the desktop information sources by using a single location for allnotifications to a user. One example of this is Octel™ UnifiedMessenger™ product and Call Pilot™, both operable with a PABX system andavailable to operate with a message server 164 such as Microsoft™Exchange or Lotus Domino. These products can already delivery voicemessages into the user's e-mail inbox for later retrieval andmanipulation via the user's desktop computer and the user never has totouch the phone to replay the message. Data switches can open up a phoneconnection on a TCP/IP connection, also called Voice over IP (VoIP). AVoIP connection from a workstation over data-centric wireless network145 to mobile device 100 can be established as an alternate to the useof a voice network. It is possible that a VoIP connection could bere-routed directly to the mobile device 100 by wireless connector 125,either via a voice channel or via a data channel. Making this connectionover a data channel in wireless network 145 will require high datatransfer rates. VoIP connections are one of a class of connectionsreferred to as Voice over Packet connections. One of skill in the artwill readily appreciate that the above discussion is not limiting thescope of the invention to VoIP connections, and instead any connectionof the broader VoP class of connections can be easily adapted for usewith mobile device 100.

An example is now described. First, the origination of data items 205may occur on a computer system Y connected to the Internet 135, the dataitems 205 may then flow into the corporate environment through thefirewall 162 and are stored at a data store 165 associated with themessage server 164. Similar data items (not shown) may also be stored atthe data store 165 that are generated at one of a plurality ofworkstations coupled to the corporate LAN. Alternatively, a data storemay be at each desktop computer 120.

Second, when the wireless connector software 125 detects the data items205 at the data store 165 desktop workstation or network server 120 andit matches the forwarding criteria set up by the user. The user hasdirect control at their workstation to limit, filter and monitor alldata items 205 that could be sent, via the wireless network 145, totheir mobile computer 100. The wireless connector program 125 uses allavailable information and resources to determine; (a) when to send, viathe wireless network 145, data items 205 based on triggers like locationinformation, heat sensors, motion detectors and screen savers, (b)configured information from the user like filters, desired data types205 and mobile computer 100 capabilities, and finally the continuousarrival of these data items 205.

Finally in step (C1) or (C2) the wireless connector 125 re-envelopes thedata items 215 so that complete transparency is maintained for thesender and the receiver of the message. This also means that alladdressing information, subjects and content is kept intact provided themobile device can support all elements of the original data item 205.FIG. 2 shows both mail messages or phone calls 205 arriving to thedesktop workstation or network server 120, but the numbers and types ofdata items 205 are not limited to only these types. Once the originaldata item 205 is re-enveloped as data item with reference 215 and thisreenveloped data item is delivered along a path to the data-centricwireless network 145. The reenveloping of data item 205 into data item215 may result in data item 215 capable of transmission via TCP/IP.There are at least two possible paths. These paths are shown as (C1) and(C2), although others could also be possible. In a first embodiment, thedata is sent via the Internet to a wireless gateway 140, labeled C2. Awireless gateway 140 is often used to improve the speed and quality ofthe delivery of data items 205 over the data-centric wireless network tothe mobile computer 100. It may act as temporary data store ofinformation exchanged, via the wireless network, between the host system160 and the mobile device 100. Alternatively the data could also be sentusing a wireless Virtual Private Network (VPN) router to the mobiledevice 100 over the Internet 135, labeled C1. A person skilled in theart would also appreciate that there may be many other methods to reacha data-centric wireless network 145 other then the Internet 135 such asa private, dedicated point-to-point connection, like PSTN, ISDN or FrameRelay. The step of traversing through paths (C1) or (C2) may beoptionally skipped when the device is docked at its serial cradle whichis in communication with a desktop computer system 120 via communicationlink 105. In such an instance, the user may not want any data items 215forward to the mobile computer 100 when they are sitting at theirdesktop computer system.

The present invention allows data to be securely sent via a wirelessnetwork to the mobile device 100, when criteria are met, it providesdata sending from numerous data types including phone calls, email anddata on a secure network. This communications method allows usermobility, as the user's data follows him wherever he travels. Since allof these steps take place securely, from behind a firewall 162, it iscompletely suitable for an environment with sensitive data. Thisre-enveloping technique allows for full compression and encryption totake place before it leaves wireless connector 125 to the mobile device100. For those skilled in the art, the firewall 162 is generallyacknowledged as a reasonable security wall that keeps Intranet-basedinformation secure from the prying eyes of public Internet users. One ofskill in the art will readily appreciate that numerous modifications tothe technique of data pushing can be easily implemented withoutdeparting from the scope of the present invention. Additionally, one ofskill in the art will appreciate that the above lists of data types thatcan be sent, via a wireless network, to the mobile device is merelyexemplary, and should not be viewed as exhaustive.

Although not shown, a person with a set of earphones running from themobile device 100 up to their ears. One of skill in the art willrecognize that the hands free headset can be varied with numeroussimilar devices known in the art. An advantage if the hands free headsetis that as the user talks she has her hands free to type, performtouch-screen actions and perform menu selections on mobile device 100.This allows her to deal with voice and data issues simultaneously,whether or not the issues are related. For example the user mightreceive a call from Person Y, and decide to send an unrelated message toPerson W while still engaged with the call, to save time. Alternatively,the user might receive e-mail from Person Y, and decide to call Person Yafter reading the e-mail to deal with an urgent matter.

Turning now to FIG. 2 this is an illustration of some components of amobile device 100 and how the arrival of a data message 430 can causethe initiation of a voice call connection by the voice component of themobile device. In this exemplary illustration, an incoming message 430triggers logic on the mobile device 100 that enables the user toautomatically call back the sender or another number that might appearwithin the subject or body of the message. The call-back feature cancross-reference the sender's email address to one of a plurality ofnumbers in the PIM data stored in either a data store 165′ at mobiledevice 100 or the data store 165 at host system 160 (not shown).

FIG. 2, the first step is a message with contents ‘A’ leaving Person Y'sdesktop computer system (shown in FIG. 1) destined to reach the datastore 165 of computer 120 which is associated with mobile device 100.The message 420 is analogous to data 205 in FIG. 1 as message 405 isconsidered just another data item as it arrives, and is provided towireless connector 125. Within the company's corporate LAN environmentthe message 420 is then compressed, encrypted and re-enveloped, there-enveloped message is shown as incoming data message 430, before it issent, via the wireless network 145, to the mobile device 100. The nextstep is the delivery of message ‘A’ through the data-based wirelessnetwork 145 to the mobile device 100. Depending on the network thedata-based wireless network 145 and voice-based wireless network 150 canbe integrated, as is the case for GSM and GPRS, or superimposed uponeach other.

Once the message is received by mobile device 100 the user is preferablynotified and the message is opened for viewing on the display of thedevice so that to the user may start reading the contents 440 of messageA. The message could be an email message, a calendar message, a memo-padmessage or any other PIM message that could contain relevant informationto the user. This is an example of the presently preferred embodiment ofthe invention when an e-mail message is transmitted to and received bymobile device 100. When a software or firmware module is displaying thee-mail message, as with most incoming data such as calendar or meetingrequests, the message will have a sender, indicated in this example bythe underlined ‘From: Person Y’ line item. Preferably, the user of themobile device may scroll through the message he is viewing by one ormore navigation means, including but not limited to roller-wheels,thumbwheels, jog dials, cursor keys, touch screen navigation controls.The user can move the cursor to the “from” field. Preferably, either amenu selection appears automatically or alternatively the user invokes amenu selection by input via the navigation or selection means. In apreferred embodiment, a menu item such as ‘Call Address’ is offered asan action among the one or more menu selection action items. Anillustrative menu selection is shown in FIG. 2 b. As shown, the menuselection 451 graphical user interface (GUI) may include one or more ofthe following action items: hide menu 452, copy 454, mark unopened 456,file message 458, save message 460, reply 462, forward 464, reply to all466, delete 468, more 470, email person y 472, SMS person y 474, callperson y 476, view contact info 478, show qualified address 480,previous item 482, next item 484, next unopened item 486, close 488.

In the case where the user selects “call person y” 476 a menu process isinvoked. This process can perform several functions. In one case, thedata handling component searches a local PIM data store 165′ accessibleby the software or firmware to determine if there is a contact entryassociated with the selected sender's e-mail address or qualified nameassociated with the e-mail address. The search criterion of the searchof the PIM data store may be based on the sender's email address in thee-mail message 440. If more than one phone number is located, the datahandling component preferably prompts the user to select which phonenumber of the plurality is desired for the outbound voice call (as shownin 450). Alternatively, if no entry associated with the address isfound, the user can be prompted to input a phone number for this contact(not shown). Once the phone number is selected the data handlingcomponent of mobile device 100 transmits a request to the cellular phonecomponent to initiate an outbound voice call from the device 100 to theselected phone number. The necessary components of the cellular phonecomponent of the mobile device then initiates (as shown in 451) andestablishes an outbound voice call with the information at leastpartially collected from the data store 164′.

FIG. 3 is a flow chart that illustrates an illustrative embodiment ofthe method associated with FIG. 2. This flow chart provides details toimplement a method of making a cell phone call from an incoming dataitem. The first step is that mobile device 100 receives a data item 505on the data component of the device. The data item 505 is checked toverify it is a viewable data item 510. This data message could be acommand and control message, or it could be a continuation of anexisting message. If the data message is a command message, a controlmessage or some other continuation of existing data 515, it might notsupport a traditional sending address or other data fields. If thecontents of the data item are displayable they are presented to the userfor viewing 520.

During the viewing process the user can select a menu item to input acommand 525. In a preferred embodiment, one or more the commands setforth in FIG. 2 a are available to the user including the command ‘CallPerson Y’. In this example, at step 530 the user can either select Callor another menu command item. If the user selects another command it isprocessed 535. If the user selects ‘Call’ 530 then mobile device 100proceeds to check to see if the user has highlighted the address fieldof the message 540. This field could be any address field in the dataitem, in FIG. 2 the example is the ‘From’ field but other fields wouldwork just as well. The ‘To Field’, ‘Carbon Copy (CC) field, or the ‘FromField’, could all be used. For one skilled in the art it is clear that amessage, like one produced in e-mail, could have many TO and many CCfields/e-mail addresses listed within it. Additionally, if the messagecontains a third party's contact information, highlighting theinformation can allow a call to be made to the third party.

If the field the user has highlighted is not an address field otherprocessing will be performed 545. This step cross-references to tab ‘REFA’, which contain other aspects of the invention. If the field is theaddress field it is checked against a contact list in the PIM data tosee if an associated reference exists 550. For one skilled in the art itis clear that this address matching may have already been performed sothat a ‘friendly name’ can be displayed to the user. Regardless of whenthe search was performed, the address is either associated with acontact entry or it is not. If there is no contact entry associated withthe highlighted field the user is prompted to enter a number for thenamed user 555. This number is then provided to the voice-centriccomponent to dial the number 560. If the address field does match acontact entry then a check 565 is performed to see how many numbersexist for this contact entry. If there is more than one phone number inthe contact database the user is prompted to select one 570, which isgiven to the dialer to call 560. If there is only one number the numberfor the contact entry it is given to the dialer to call 560. Once thecall is established the user is connected to the addressee, and canstill read message 580.

FIG. 2 c is a block diagram of a mobile device 100 that may be used bythe invention herein. The device 100 includes a transceiver 11, amicroprocessor 38, a display 22, Flash memory 24, RAM memory 26,auxiliary input/output (I/O) devices 28, a serial port 30, a keyboard32, a speaker 34, a microphone 36, a short-range wireless communicationssub-system 40, and may also include other device sub-systems 42. Thetransceiver 11 preferably includes transmit and receive antennas 16, 18,a receiver 12, a transmitter 14, one or more local oscillators 13, and adigital signal processor 20. Within the Flash memory 24, the device 100preferably includes a plurality of software modules 24A-24N that can beexecuted by the microprocessor 38 (and/or the DSP 20), including a voicecommunication module 24A, a data communication module 24B, and aplurality of other operational modules 24N for carrying out a pluralityof other functions.

The mobile communication device 100 is preferably a two-waycommunication device having voice and data communication capabilities.Thus, for example, the device may communicate over a voice network, suchas any of the analog or digital cellular networks, and may alsocommunicate over a data network. The voice and data networks aredepicted in FIG. 1 by the communication tower 19. These voice and datanetworks may be separate communication networks using separateinfrastructure, such as base stations, network controllers, etc., orthey may be integrated into a single wireless network.

The communication subsystem 11 is used to communicate with the voice anddata network 19, and includes the receiver 12, the transmitter 14, theone or more local oscillators 13 and may also include the DSP 20. TheDSP 20 is used to send and receive signals to and from the transmitter14 and receiver 12, and is also utilized to receive control informationfrom the transmitter 14 and to provide control information to thereceiver 12. If the voice and data communications occur at a singlefrequency, or closely-spaced set of frequencies, then a single localoscillator 13 may be used in conjunction with the transmitter 14 andreceiver 12. Alternatively, if different frequencies are utilized forvoice communications versus data communications, then a plurality oflocal oscillators 13 can be used to generate a plurality of frequenciescorresponding to the voice and data networks 19. Although two antennas16, 18 are depicted in FIG. 1, the mobile device 100 could be used witha single antenna structure. Information, which includes both voice anddata information, is communicated to and from the communication module11 via a link between the DSP 20 and the microprocessor 38.

The detailed design of the communication subsystem 11, such as frequencyband, component selection, power level, etc., will be dependent upon thecommunication network 19 in which the device is intended to operate. Forexample, a device 100 intended to operate in a North American market mayinclude a communication subsystem 11 designed to operate with theMobitex™ or DataTAC™ mobile data communication networks and alsodesigned to operated with any of a variety of voice communicationnetworks, such as AMPS, TDMA, CDMA, PCS, etc., whereas a device 100intended for use in Europe may be configured to operate with the GeneralPacket Radio Service (GPRS) data communication network and the GSM voicecommunication network. Other types of data and voice networks, bothseparate and integrated, may also be utilized with the mobile device100.

Depending upon the type of network 19 (or networks), the accessrequirements for the mobile device 100 may also vary. For example, inthe Mobitex and DataTAC data networks, mobile devices are registered onthe network using a unique identification number associated with eachdevice. In GPRS data networks, however, network access is associatedwith a subscriber or user of a device 100. A GPRS device typicallyrequires a subscriber identity module (“SIM”), which is required inorder to operate the device 100 on a GPRS network. Local or non-networkcommunication functions (if any) may be operable, without the SIMdevice, but the device 100 will be unable to carry out any functionsinvolving communications over the data network 19, other than anylegally required operations, such as 911 emergency calling.

After any required network registration or activation procedures havebeen completed, the dual-mode device 100 may the send and receivecommunication signals, including both voice and data signals, over thenetwork 19 (or networks). Signals received by the antenna 16 from thecommunication network 19 are routed to the receiver 12, which providesfor signal amplification, frequency down conversion, filtering, channelselection, etc., and may also provide analog to digital conversion.Analog to digital conversion of the received signal allows more complexcommunication functions, such as digital demodulation and decoding to beperformed using the DSP 20. In a similar manner, signals to betransmitted to the network 19 are processed, including modulation andencoding, for example, by the DSP 20 and are then provided to thetransmitter 14 for digital to analog conversion, frequency upconversion, filtering, amplification and transmission to thecommunication network 19 (or networks) via the antenna 18. Although asingle transceiver 11 is shown in FIG. 1 for both voice and datacommunications, it is possible that the device 100 may include twodistinct transceivers, a first transceiver for transmitting andreceiving voice signals, and a second transceiver for transmitting andreceiving data signals.

In addition to processing the communication signals, the DSP 20 alsoprovides for receiver and transmitter control. For example, the gainlevels applied to communication signals in the receiver 12 andtransmitter 14 may be adaptively controlled through automatic gaincontrol algorithms implemented in the DSP 20. Other transceiver controlalgorithms could also be implemented in the DSP 20 in order to providemore sophisticated control of the transceiver 11.

The microprocessor 38 preferably manages and controls the overalloperation of the dual-mode mobile device 100. Many types ofmicroprocessors or microcontrollers could be used here, or,alternatively, a single DSP 20 could be used to carry out the functionsof the microprocessor 38. Low-level communication functions, includingat least data and voice communications, are performed through the DSP 20in the transceiver 11. Other, high-level communication applications,such as a voice communication application 24A, and a data communicationapplication 24B may be stored in the Flash memory 24 for execution bythe microprocessor 38. For example, the voice communication module 24Amay provide a high-level user interface operable to transmit and receivevoice calls between the dual-mode mobile device 100 and a plurality ofother voice devices via the network 19. Similarly, the datacommunication module 24B may provide a high-level user interfaceoperable for sending and receiving data, such as e-mail messages, files,organizer information, short text messages, etc., between the dual-modemobile device 100 and a plurality of other data devices via the network19. The microprocessor 38 also interacts with other device subsystems,such as the display 22, Flash memory 24, random access memory (RAM) 26,auxiliary input/output (I/O) subsystems 28, serial port 30, keyboard 32,speaker 34, microphone 36, a short-range communications subsystem 40 andany other device subsystems generally designated as 42.

Some of the subsystems shown in FIG. 1 perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as keyboard 32 and display 22may be used for both communication-related functions, such as entering atext message for transmission over a data communication network, anddevice-resident functions such as a calculator or task list or other PDAtype functions.

Operating system software used by the microprocessor 38 is preferablystored in a persistent store such as Flash memory 24. In addition to theoperation system, which controls all of the low-level functions of thedevice 100, the Flash memory 24 may include a plurality of high-levelsoftware application programs, or modules, such as a voice communicationmodule 24A, a data communication module 24B, an organizer module (notshown), or any other type of software module 24N. The Flash memory 24also may include a file system for storing data. These modules areexecuted by the microprocessor 38 and provide a high-level interfacebetween a user of the device and the device. This interface typicallyincludes a graphical component provided through the display 22, and aninput/output component provided through the auxiliary I/O 28, keyboard32, speaker 34, and microphone 36. The operating system, specific deviceapplications or modules, or parts thereof, may be temporarily loadedinto a volatile store, such as RAM 26 for faster operation. Moreover,received communication signals may also be temporarily stored to RAM 26,before permanently writing them to a file system located in thepersistent store 24.

An exemplary application module 24N that may be loaded onto thedual-mode device 100 is a personal information manager (PIM) applicationproviding PDA functionality, such as calendar events, appointments, andtask items. This module 24N may also interact with the voicecommunication module 24A for managing phone calls, voice mails, etc.,and may also interact with the data communication module for managinge-mail communications and other data transmissions. Alternatively, allof the functionality of the voice communication module 24A and the datacommunication module 24B may be integrated into the PIM module.

The Flash memory 24 preferably provides a file system to facilitatestorage of PIM data items on the device. The PIM application preferablyincludes the ability to send and receive data items, either by itself,or in conjunction with the voice and data communication modules 24A,24B, via the wireless network 19. The PIM data items are preferablyseamlessly integrated, synchronized and updated, via the wirelessnetwork 19, with a corresponding set of data items stored or associatedwith a host computer system, thereby creating a mirrored system for dataitems associated with a particular user.

The mobile device 100 may also be manually synchronized with a hostsystem by placing the device 100 in an interface cradle, which couplesthe serial port 30 of the mobile device 100 to the serial port of thehost system. The serial port 30 may also be used to enable a user to setpreferences through an external device or software application, or todownload other application modules 24N for installation. This wireddownload path may be used to load an encryption key onto the device,which is a more secure method than exchanging encryption information viathe wireless network 19.

Additional application modules 24N may be loaded onto the dual-modedevice 100 through the network 19, through an auxiliary I/O subsystem28, through the serial port 30, through the short-range communicationssubsystem 40, or through any other suitable subsystem 42, and installedby a user in the Flash memory 24 or RAM 26. Such flexibility inapplication installation increases the functionality of the device 100and may provide enhanced on-device functions, communication-relatedfunctions, or both. For example, secure communication applications mayenable electronic commerce functions and other such financialtransactions to be performed using the device 100.

When the dual-mode device 100 is operating in a data communication mode,a received signal, such as a text message or a web page download, willbe processed by the transceiver 11 and provided to the microprocessor38, which will preferably further process the received signal for outputto the display 22, or, alternatively, to an auxiliary I/O device 28. Auser of dual-mode device 100 may also compose data items, such as emailmessages, using the keyboard 32, which is preferably a completealphanumeric keyboard laid out in the QWERTY style, although otherstyles of complete alphanumeric keyboards such as the known DVORAK stylemay also be used. User input to the device 100 is further enhanced witha plurality of auxiliary I/O devices 28, which may include a thumbwheelinput device, a touchpad, a variety of switches, a rocker input switch,etc. The composed data items input by the user may then be transmittedover the communication network 19 via the transceiver 11.

When the dual-mode device 100 is operating in a voice communicationmode, the overall operation of the device 100 is substantially similarto the data mode, except that received signals are preferably be outputto the speaker 34 and voice signals for transmission are generated by amicrophone 36. Alternative voice or audio I/O subsystems, such as avoice message recording subsystem, may also be implemented on the device100. Although voice or audio signal output is preferably accomplishedprimarily through the speaker 34, the display 22 may also be used toprovide an indication of the identity of a calling party, the durationof a voice call, or other voice call related information. For example,the microprocessor 38, in conjunction with the voice communicationmodule and the operating system software, may detect the calleridentification information of an incoming voice call and display it onthe display 22.

A short-range communications subsystem 40 may also be included in thedual-mode device 100. For example, the subsystem 40 may include aninfrared device and associated circuits and components, or a Bluetooth™short-range wireless communication module to provide for communicationwith similarly-enabled systems and devices.

Turning now to FIG. 4 this illustration is another embodiment ofhandling incoming data to perform outgoing phone calls, as was FIG. 2.This illustration depicts the ability for the invention to scan normaldata fields and identify embedded phone numbers. Linking a non-addressfield arriving on an incoming data item, to an outgoing voice event is afeature of this aspect of this invention. A phone number scanningprocess allows a data message to trigger special logic on the mobiledevice 100 that enables the user to automatically call back any numberthat might appear within the text of the data message 440.

Although not shown in FIG. 4, the various components of the mobiledevice as discussed with respect to FIG. 16 would equally apply hereincluding local data store 165′ (shown in FIG. 2). In FIG. 4, the firststep shown is a message 420 with contents ‘B’ leaving Person Y's desktopcomputer system 410 destined to reach the desktop of the user that ownsthe mobile device 100. The data items is analogous to message 205 fromFIG. 2 as it is considered just another data item as it arrives atwireless connector 125. Within the company's firewalled environment 160,the message is compressed, encrypted and reenveloped 430 and then issent, via the wireless network 145, to the mobile device 100. Step 2 isthe delivery of message ‘B’ through the data-based wireless network 145to the mobile device 100.

Once the message is received the user is notified and opens the messageto start reading what was sent 610. In this case the data viewer couldbe an e-mail viewer, a calendar view, a todo list view, a task view, anexpense report viewer, a database viewer, an Internet browser, aWireless Access Protocol (WAP) browser, or any proprietary data viewerthat might be receiving data items from a host system. Naturally theviewer selected would match the data item, like an e-mail message, acalendar message, a todo item, a memo-pad message, expense report data,a database record, an HTTP, XML, WML or HDML markup page.

During the viewing process the user can move the cursor through the dataitem and highlight a phone number. In FIG. 4 the example used is ane-mail message with a phone number reference to a third-party colleague,Person W. Person W is not in the contact list, but by selecting thephone number by rolling over it, highlighting it, or otherwiseindicating it in a manner that would be known to one of skill in theart, the user can select the ‘Call Number’ menu option to perform adynamic call to the selected number, shown as step 3.

Once the user selects a string to call on, the software or firmware onthe mobile device 100 proceeds to verify the string as a real phonenumber 620. Once the string is verified mobile device 100, step 4 is tosubmit the phone number string to the voice component for dialing. Thisis the same voice component as used in the example of FIG. 2. In anadvanced embodiment of the invention the phone string scanner can lookforward and backward from the cursor to find a valid phone number if oneis not selected.

Turning now to FIG. 5 this illustrates a flow chart of how mobile device100 scans for phone numbers in data items arriving on the data componentof the mobile device 100. This flow chart is cross-referenced to FIG. 3with a tag labeled REF A. Reference A occurs as the user selects a menuitem to ‘Call Number’ and has not highlighted or selected an addressfield, or the address field is not numeric.

Step 1 of FIG. 5 is a test to see if the cursor is currently sitting ona phone number character 705. A phone number character would alsoinclude brackets ‘(‘and’)’ and a dash ‘-’ character. These charactersare allowed for syntax and readability reasons and they are commonlyused in the art. If the current character not a valid phone numbercharacter then the software will scan in either direction looking for avalid phone character 710. Then if a valid phone character is found inthe scan 715 the invention proceeds to parse and check for a full phonenumber 720. If no valid phone character is found at 715, then theinvention might proceed to other forms of call processing such asmapping a mixed string of number and letters to a phone number based onthe letters typically assigned to the keys of telephone (e.g. ‘HAM’would be mapped to ‘416’).

Similarly from 705 if the current character pointed to by the cursor isalready a phone number character the invention proceeds directly to thefield parser to look for a whole phone number 720. If a full phonenumber cannot be verified the user is informed with an error message725. If a phone number is detected then the number is given to the voicecomponent 730 to dial the number found. Once the call is initiated theuser is connected to the caller 735.

In this next section we explore three ways of providing similar advanceddata and voice integration. These three examples in FIGS. 6, 7 and 8show how an incoming message can be used to generate a conference callon the voice component of the mobile device.

Turning now to FIG. 6, in this solution the first step is the arrival ofa data item 810 from wireless connector 125. In a presently preferredembodiment the data item is an e-mail message that has been compressedand encrypted before leaving the company firewall towards the datacomponent of the mobile device 100. It is possible that the data item isalso a work flow item, a web page, or even a proprietary database item.Once it arrives it is opened by the user and displayed in a data viewthat matches the type of information received 820. In this example thee-mail message is shown and lists just one ‘To’ field, three ‘CC’ fieldsand one ‘From’ field. For one skilled in the art it is clear that aphone number to be conferenced could also come from the body of themessage using the scanning technique shown in FIG. 4.

At any time during the viewing process the user can roll to an addressfield and select a menu ‘Conference Address’. This method is similar tothe approach taken in FIG. 3 and show through the flow chart in FIG. 3.Step 2 takes place once the user does decide to start a conference calland selects an address to call. Once the addressee is selected,verification is performed 830 to ensure there is a number for theaddressee; either in the contact list or hand entered by the user. Thesesteps are also described in greater detail in FIG. 2 and the data flowFIG. 3. Once the phone number is verified the invention passes the phonenumber to be conferenced to the cell phone component for dialing 840.This step is the same for all the numbers provided to the cell phone, nomatter where they were located. Once the call is completed the user andthe called party have a private conversation until the user selects themenu again. At this menu the mobile device user can either join theconference, or proceed to add more conference attendees. This isdescribed in detail in the data flow diagram illustrated in FIG. 9.

Turning now to FIG. 7 we see another embodiment of the same conferencecall ability shown with FIG. 6. In this solution the first step is thearrival of a data message that in this example carries a new calendarevent. In the case where this calendar event is a proposed meeting orappointment request and the request is ‘accepted’ by the user at themobile device 100, the PIM software functionality of the devicepreferably sometime later will alert the user to the meeting start time.In one embodiment, this meeting request is that it will also contain thephone numbers of the other participants on the call that can be used toestablish the calls when the meeting approaches. The phone numbers ofattendees may be added to the meeting request data message prior totransmission from the host system to the mobile device. Alternatively,the phone numbers of the attendees may be added at the mobile devicebased on data derived from the local PIM data store. This short-cut andmany others are very easy to achieve in a true mobile device, this isbuilt from the ground up to handle normal data events and PIMinformation that a desktop system could be processing.

Step 1 of FIG. 7 illustrates a new data item 910 leaving the user'sdesktop system, via the wireless connector program 125. Before thiscalendar event 910 leaves the secure company firewall 162, it iscompressed, encrypted and re-enveloped for delivery to the mobile device100. The packaged calendar event traverses the Internet and then iscommunicated through the data-based wireless network to the mobiledevice 100 via its RF link. Once received the message is opened,unencrypted, uncompressed and presented to the user via the calendar UI920. The UI can be done in many ways, but in this simple example themeeting time, location (if relevant), and attendee list is provided.With the attendees is the phone number for each attendee, which can beused later by the invention.

Sometime after the user has accepted to new calendar event the calendaralarm fires as part of step 2 in this example. As one skill in the artof UI design and PIM/User interaction can appreciate the calendar on thedevice will attempt to notify the user when the event approaches. Thereare several ways to notify the user before the event is reachedincluding but not limited to: running a vibrator, blinking a light,sounding an alarm, popping up a notification box on the screen or somecombination of the above. The user can select the amount of time beforethe event takes place before starting the alarm, the user can alsoselect the alarm method, i.e. vibration, beeping or a combination of thetwo. In step 2 the alarm box appears for the user 930 to inform them themeeting is approaching. In this example the user of the mobile device100 is in charge of the meeting and a conference call is planned 930.This invention would work just as well if only one other person wereinvolved in this meeting, but the fact there are three people makes theinvention even more useful.

Step 3 takes place with the alarm screen in front of the user, they areable to select each of the attendee's names and request a ‘ConferenceCall’ be made to that person. The selection might involve using astylist on a touch screen, scrolling to the name and pressing a key, orselecting a menu item. Step 3 verifies the name provided, perhaps bypulling the phone number out of the contact database, and requests thecell phone voice component of the mobile device 100 to make the call840. This is the same request made in FIG. 6 there is no difference. Thecall is then made to a person's phone 850, assuming they answer thecall, and once the circuit is completed the user can talk to theattendee and conference them into the other calls parked on the device.Once the call is complete the user can at any time select a menu and goretrieve another call or join the conference. It is well known to anyoneskilled in the art of telephony how conference calls are achieved andestablished so this step is not described further, see FIG. 9 for moredetails. As each attendee is called they are progressively placed intothe conference call hosted by the user of the mobile device 100. As onecall completes, or fails, the user is returned to the original UI screenfor the alarm event 930 where they can scroll to the next attendee andrequest a call be made to him or her. Once all attendees have been triedand conferenced in, naturally some attendees may not be reachable, theconference can start and the user can join in with the last attendee.The ability for the user to scroll and perform minimal keystrokes tostart the conference call makes the mobile device 100 an invaluable toolfor completing such a complex task with such a small form-factor type ofdevice.

Turning now to FIG. 8 there is another illustration of advanced methodto perform a conference call from an incoming data item. Step 1 in thisexample occurs when a data item 1010 is prepared and leaves the user'sdesktop or company environment. This data item 1010 may have beenprepared manually by a secretary, or generated automatically by someworkgroup management software running in the corporate environment 160.As it arrives to the mobile device 100 via the data-based wirelessnetwork 145 the user opens the item for viewing 1020. Once opened forviewing the user realizes it is a task list containing personal taskinformation. In this example the tasks are part of a project thatinvolves many members working together in a project team or workgroup1020. For anyone skilled in the art of workgroup software it is clearthat there are many available products that perform advanced workgroupmanagement within a LAN environment. Some of the newer products can evendo full workgroup management through the Internet.

Step 2 of FIG. 8 takes place when the user decides that something needsto be done about a given task item 1030. Within the workgroup managementUI the user selects the ‘Start Conference’ menu item and begins to callpeople. Just as in FIG. 7 each user is selected by rolling the cursor tothe user's name or number and selecting the Conference Attendee menuitem. This can also be easily achieved using touch screen methods bytouching the user's name or number to begin the conference call. Asalways the software verifies the number, or allows the user to select anumber from the contact database 1040. Once this is complete it ispassed to the cell phone component 840 to start the call. Once theattendee is reached the user has a brief conversation with the attendeeand then joins them into the conference. This method proceeds until allnecessary attendees are joined into the call and the user finally joinsthe conference. Note that it is not essential that every single personon the workgroup actionable item to join the call, only the attendeesthe user deems necessary.

Turning now to FIG. 9 this diagram provides a flow chart that describesthe steps to create a conference call from a data item within a mobiledevice. As with FIG. 5, FIG. 9 also references back to the flow chart inFIG. 3. From FIG. 3 we have the reception of data items 505 that areverified to be viewable by the user 510. Once the user has opened themand viewed them 520 they select the menu 525 to input a command like‘Call’ 530. If the cursor is not sitting on an address field 540 thenmore advanced processing is required 545 and we reach REF B that takesthe user to FIG. 9.

In FIG. 9 we have several ways to reach step 1 at 1105. Coming from FIG.3 the user is viewing a normal data item (REF B), the user might beviewing a calendar alarm, or they may have opened a pre-existing dataitem, like a task list. With this data item open the user is normallyscanning the information and consider what they want to do. In the caseof FIGS. 8, 9 and 10 the user is considering starting a conference calland have invoked the menu and issued a command like ‘Call’ or ‘StartConference’ and is about to select one or more conference callattendees.

At this point the software in the mobile device 100 must determineexactly what the user wishes to do. The system is flexible enough thatthey might take several names from the address field of the data item,combine that with phone numbers in the body of the message, or pull themfrom a calendar alarm. Wherever the phone numbers come from the usersimply iterates through the data available adding attendees to theconference. Proceeding from step 1105 the software determines where thecursor is currently sitting and what does the user want to do. At step1110 the software determines if the cursor is on an address field. Theaddress field might simply be defined by the syntax, or it could bedefined by an existing reference to an entry in the contact database. Ifit is not sitting on an address field the software checks to see if thecursor is pointing to a valid phone number character 1115. As mentionedbefore this could be a number from 0 to 9, a bracket ‘(‘or’)’ or itcould be a dash ‘-’. If the cursor is not directly over a valid phonenumber character then it will scan a few characters in either directionfrom the cursor looking for a valid phone character 1120. If a validphone character is found at this stage the field parser checks for acomplete phone number 1125. If a phone number is found it is presentedto the user for confirmation before the call takes place 1140. If nophone number is found an error is displayed 1130, the field is ignoredand the user is returned to the message to scan further for otherattendees to add to the conference call 1105.

Returning to step 1115 if the cursor is sitting on a valid phone numbercharacter then an attempt is made to confirm that a full phone number ispresent 1135. If the valid phone number character does not represent aphone number then the software will scan a few characters in eitherdirection looking for another valid phone number character 1120. Ifanother character is found a further test is preformed 1125 looking fora phone number. If there is no phone number the field is ignored and anerror message is displayed 1130. Otherwise the number is confirmed tothe user 1140 and will be even eventually used to dial the cell phonecomponent 1145.

Returning back to step 1110 if the cursor is currently pointing to anaddress field the process proceeds to Reference C (‘REF C’). Reference Cgoes to FIG. 13, which performs a search of the contact database andresolves the address entry to a phone number. Once the address field isreduced to a phone number it is provided to the cell phone dialer tocall the number 1145. Once the attendee is reached they have a briefconversation 1155 with the user of the mobile device 100. After greetingthe user and telling them what is about to happen the user invokes acommand to either join the new attendee to the conference 1160, or tojoint the attendee and himself into the conference 1165. If they decidethat further callers are required they proceed back to the scanning step1105 to look for another name or number to call. If for some reason theygo back to step 1105 and cannot find any other phone number or attendeesthey can take a short cut directly back to join the existing conferencecall 1165.

FIG. 10 illustrates the method of receiving a telephone call, and thesubsequent actions of mobile device 100 for handling the call andproviding the user with the benefits of true integration of the voiceand data components. In this example a phone call arrives in from PersonY and causes one or more data related events to take place. These dataevents can be configurable by the user but normally follow a preferredorder. This illustration also presents one possible use of the Caller Id(CID) when present. Most calls contain caller id information, thoughcalls from overseas, and from parties wishing to block the caller idinformation, will arrive at mobile device 100 without caller idinformation. Though typically the caller id information is used todetermine the actions taken by the data component of mobile device 100,there are still automatic actions that can take place if the Caller Idinformation is absent. As calls arrive, the user has the ability to opena contact database record, or create a new contact record based on theincoming caller id information if the number provided cannot be matchedto one in the address book. This action allows the user to populate thecontact information stored by the mobile device on an ongoing basis toprovide the most up to date information possible. This also allows otherdata-centric events to be performed on the data, either upon receipt ofthe caller id in a subsequent call, or from a data component initiatedevent.

The term Caller Id (CID) is also termed Calling Number Delivery (CND) orCalling Number Identification (CNI), came about as an extension ofAutomatic Number Identification (ANI). The transmission of CIDinformation takes place between the first and second ring. Theinformation sent typically includes the date, time, and calling number.The name associated with the calling number may also be included. TheCID is transmitted by a variety of interconnected wireless networks sothat this information reaches the voice component of the mobile device100.

Step 1 of FIG. 10 occurs when a voice call arrives again from anexternal phone caller, labeled Person Y (470), and arrives into themobile device 100. Each call will either have Caller Id information orit will not have that information present, in both cases the user ispresented with an indication that a call is arriving 1210. Thisindication may be a visual alert, an audio alert, or a vibrating alert.In the event that no Caller Id information is present the user has lessinformation presented to help them make the decision about whether toaccept or reject the call 1210. When Caller ID information is presentthe user is presented with all available information and the cell phonecomponent will notify the user of the call and present a dialogue box sothey can accept or reject the call 1210.

After the call is accepted step 2 takes place, under the direction ofthe user's configured preference (P). In this example the preference,labeled ‘P’, can take the user to (A) directly todo a contact databaselookup 1230 (B), to the call log 1240 or directly (C) to the e-mailcompose area 1220. For one skilled in the art it is clear that thearrival of an incoming call could take the user to any number of datacentric sub-systems including: the task/to do subsystem, the expensereporting subsystem, the time reporting subsystem, the calendarsubsystem. One of skill in the art will readily appreciate that thepreceding list is merely exemplary and is not exhaustive. In thepreferred embodiment the user configures the mobile device 100 tolook-up the incoming phone number in the contact database 1230, alsoreferred to as a an address book, where each record in the contactdatabase is referred to as an address book entry. This is very handywhen the incoming Caller Id does not include alphabetic text for theincoming call, just a phone number. Once the contact entry has beenlocated the invention will automatically take the user directly into theCall Log area so that notes on the call can be taken 1240. For a busyexecutive, a salesperson or a lawyer this kind of time tracking methodwould be indispensable to their daily workday. If the Caller Idinformation is not present the invention can direct the user directlyinto the Call Log area where the caller's name can be input manuallyduring the duration of the call, or upon completion of the call. Sincethe user can receive the call with their earphone or ear-bud withintheir ear their hands are free for typing on the keyboard, or using astylus on a touch screen, during the call. During this process, the usercan enter caller information, e-mail address, phone numbers, addressesand business information, just as they would in a normal PIM addressbook application.

In the preferred embodiment the contact database search can take placein two ways, although the lookup for a contact record is not limited tojust these two searches. The first search of the contact list will tryto match the Caller Id's phone number against the phone numbers alreadyin the contact database on the mobile device 100. This is the presentlypreferred first search because it is likely that the original phonenumber will be a better match to a number in the contact database.Naturally the Caller Id information will be checked against businessnumbers, home numbers and cellular phone numbers. In the event that thephone number does not match an existing entry, an intelligent patternmatching algorithm can be employed to match the Caller Id's Name to theNames in the Contact List. This match might start by looking to matchthe entire first name and last name, then just the last name, then justthe first name, etc. Finally the match might try to match the first 3digits of the first name and last digit of the last name, or somesimilar patterns to ensure that the right number of references is found.For one skilled in the art of pattern matching the above describedmethod of pattern matching will be readily understood to be merelyexemplary.

Once in the contact database search area there are several more complexpatterns that could be used to find or create a contact entry. FIG. 11illustrates some of the choices when looking for a contact entry. Oncein the call log creation step 1240 or in the compose step 1220 the usercan move back and forth as needed. This is shown by the dashed lineswith arrows in both direction. As shown in the example the user makes afew notes about the incoming call and appends them into an e-mailmessage being composed to the same user, Person Y. In this example asummary of the call is then mailed to Person Y in order to confirm themain issues discussed and agreed to. The automatic creation of an emailentry prevents the tedious efforts required to create an email messageon a form factor limited device such as the presently preferredembodiment of mobile device 100. The user can edit the name and phonenumber, as well as the categorization of the phone number in a createdentry, much as the user can select a new email address for a createdemail message, the implementation of the ability to modify theautomatically created data items will be well understood by one of skillin the art.

Turning now to FIG. 11 there is flow chart that further describes how anincoming phone call can affect the data component of the mobile device100. The first step 1305 is the arrival of an incoming phone call. Ifpresent the Caller Id information is presented to the user with a promptto accept or reject the call 1310. If the call is rejected 1315 the callwill be dropped 1320 and the user will have no further action to performwith respect to this call. Methods of dropping unaccepted telephonecalls are well known in the art. If the call is accepted 1315 the userproceeds to the preference of their choice 1325. If the preference is tocreate a Caller Log for the call 1325 they proceed to the call logsub-system 1345. If the preference is to search the contact database1330 they will proceed to 1350 and Reference C (‘REF C’), which isexpanded in FIG. 13. Otherwise there is a check to see if the user wantsto go directly into doing an e-mail compose 1335, otherwise they couldbe taken to many other choices for handling this incoming call includingcalendar, tasks or todo subsystems 1340.

Going back to step 1325 the user might be sitting within the call logsub-system taking notes on the current call 1345. At any time they couldselect a menu or button to switch subsystems. This could be done by aroller-wheel click, a specially assigned key or by a touch screenaction. Once they enter the menu select area 1360 they can decide tomove to the contact or e-mail sub-system and take information with themlike the caller id, call duration and other information. The user alsohas the choice of copying and pasting 1365 information betweensub-systems. This is shown in FIG. 10 when the user copied the call lognotes from the current call log and pasted them into an e-mail message.Going back to step 1330 the user might have decided to enter the contactsub-system. In this sub-system the user can search and create a newcontact entry to match the incoming caller 1350. These choices areexpanded in FIGS. 14 and 15, as shown by Reference ‘C’. Finally goingback to step 1335 the user could be in the e-mail compose sub-system1355 and are creating an e-mail message to send to the caller or someother person. For one skilled in the art it is obvious that whiletalking to one person it would be easy to forward a message to anotheruser recounting the phone conversation.

Turning now to FIG. 12 there is an illustration of the steps that a usermight go through as they enter the contact database area trying to matchan incoming caller id to a contract entry. In step 1 the call arriveswith or without caller id information 1210. Step 2 may take place in twoways, depending on whether caller id information was present. If thereis no caller id information the user is given the option of creating anew contact entry 1430. However, just because there is no Caller Idthere may still be a contact entry present for the caller. If this istrue the user can override the create choice and move to step 1440 wherea manual search for the address book entry can be performed.

The other way step 2 can take place is when the caller Id information ispresent, a search is started in the contact database 1410. If the searchis successful, i.e. one or more entries did match the caller id, thenthe user is taken to step 1440. If there is a list of matches for theincoming caller, it will be possible for the user, while talking to theother party, to scroll or select the correct contact entry 1440. For oneskilled in the art it is clear that this can be in many ways dependingon the device and its methods of input. Once selected, or automaticallyif there is only a single match, the user is taken to the currentcontact record for the incoming caller 1420. This record will containall the current information known about the user, which can be furtherchanged during the call itself. For example it might be that the recorddoes not yet have an e-mail address for the caller, at the end of thecall the person using the mobile device 100 might prompt the caller fortheir e-mail address.

The search might also fail to find any contact entry that matches andthe user would be taken to manually search for a contact entry 1440.They might decide there is no contact entry, and move to step 1430 tocreate one. Manually searching for contact entry is also commonly donewhen making spontaneous outgoing calls. The user might select an entryin the contact list and then scroll to a phone number in the list, i.e.home phone, mobile phone or office phone, and request to make a phonecall. This step is commonly done in most mobile phones today and is wellknow in the field. However, in this invention after the call is made thecontact record of the person called is still displayed on the displaymeans of mobile device 100. During this situation the caller can thenenter new information about the person they have just called.

Turning now to FIG. 13 this is a data flow diagram of processing anincoming phone call within the contact sub-system. As shown by ReferenceC at step 1 we have an incoming phone call, illustrated by FIG. 11. Instep 1505 the mobile device 100 may have received some information thatwill be passed to the contact sub-system, via an API call to the contactsub-system. If the Caller Id or phone number is not present 1510 theuser is taken to a choice box to create or search for the caller'sinformation 1515. If they want to create a new entry they are presentedwith a blank contact record to fill in the details 1520 for the caller.Otherwise they are presented with a list of all contacts on the mobiledevice and they can begin to narrow the list 1525.

If there was Caller Id information present 1510 then a match isattempted with the caller's phone number against all database entriesthat contain a work phone number 1530. If there are any matches they arecollected at 1550 and the process continues until all database entriesat checked. Next there is a check of the Caller phone number against thehome phone number list 1535 and finally a check is made against all thecell phones in the contact database 1540. Every match is collected andpresented to the user 1550 where they can narrow the list 1555 andselect the correct match. At any time the user can select the menuwithin the contact sub-system and move to another sub-system like thecall log or e-mail compose sub-system. Once all fields in the contactentry are searched any other fields, such as the notes field, may besearched 1545. Once this is done and all fields are exhausted 1565, theuser is presented with a selection of choices which to select thecorrect entry 1555.

Turning now to FIG. 14 there is an illustration of another advanced useof handling an incoming voice call with the data component of the mobiledevice 100. In this illustration the incoming call has only the phonenumber in the Caller Id and the user wants to uncover more informationabout the caller. This additional information might be to resolve thetrue identity of the caller, or perhaps to resolve the name of a crankcaller. Even if the name is known the user of the mobile device 100 hasthe option of getting additional information about the person or theircompany before committing too much time or money on the call itself

Step 1 of FIG. 14 is the arrival of an incoming call that is presentedto the user with just the phone number of the incoming caller 1210. FIG.14 moves to step 2 when the user accepts the call and is placed in thecontact list 1610 or the call log 1620 with no more information.

Step 3 of FIG. 14 takes place when the user decides they need moreinformation. By selecting a menu item, or by switching to the browsersub-system the user can request more information from the Internet 1630.The most common method to get more information is by performing areverse lookup on the phone number 1630. This information can beobtained through a data connection to a reverse lookup directory, andprovided seamlessly to the user. Additionally in step 3 the user mightrequest advanced information about the user or the company beingreferenced in the phone conversation, which can also be obtained usingthe data component of mobile device 100, and presented to the userseamlessly either prior, after or during the phone call conversation.

Step 4 shows the request going out to the Internet, and step 5 is aresponse returning 1660. As the user views the information in step 1660they can either copy and paste this information into the Call Log orContact entry or perhaps just use the information to deal with thecaller. Hence through the single phone call the user has been able tokeep the caller, track down their information and react to them withmore information all by using a single mobile device 100.

Turning now to FIG. 15 where a unified event list is illustrated. Theconcept of a unified event listing on a mobile device has never existeduntil now, and is essential for keeping track of all the different typesof events that can take place on a high-speed mobile device capable ofsupporting a range of media types. The goal of the unified event listingis to allow the user a quick view of what has happened over the past fewhours or days and quickly track important events and their time. Theunified event listing will have everything that has taken place on themobile device, including sent and received e-mail messages, callsgenerated by e-mail or calendar messages, web-page download requests,web forms, secure web pages, calendar messages sent or received, voicemessages, phone calls, call logs (Memo-pad entries), video calls, faxmessages, printer files, document retrievals and any other event that isimportant to the user. For one skilled in the art of Third GenerationNetworks (3G) it is clear that events like video calls, mp3 downloads,ring-tone downloads, fax messages or printer files might be a few yearsoff, but as the number of these message types increase the need for aunified event listing will increase. In the desktop world the concept ofunified event listing is sometimes called the Unified Inbox, but theterm unified event listing is more accurate to a mobile device.

FIG. 15 a shows an exemplary unified user interface 1720 for a wirelessdevice 100 that displays current communication event summary 1722unified with select stored communication events 1724. The user interface1720 includes a viewing screen 1726, a processor 1728, a transceiver1730, and a memory device 1732. The user interface 1720 also includes acommunication event software interface module 1734 that is executed bythe processor 1728. Operationally, the communication event softwareinterface module 1734 stores at least incoming and outgoingcommunication events 1736 in the memory device 1732, and enables a userto simultaneously view the current communication event summary 1722 andthe select stored communication events 1724.

The communication event software interface module 1734 preferably savesand indexes every communication event transmitted or received by thewireless device 100. In an alternative embodiment, the communicationevent software interface module 1734 may give the user the option tochoose which communication events to save and which to discard.

Each stored communication event 1736 preferably includes a communicationevent status 1738 (unread, sent, read, missed, pending, incoming,outgoing, etc.) and both a communication event type 1740 (call, e-mail,SMS, WAP, calendar, HTTP, etc.) and communication event data 1742(caller id, header information, outside number, URL, subject line,etc.). Each stored communication event 1736 preferably also includes anindex 1744 that permits the processor to cross reference additional dataassociated with the respective communication event or index. Additionaldata may include (1) more header information and the message body of thee-mail message when an e-mail message is the communication event, (2)the call log details such as notes taken by the user of the mobiledevice, the date and time of the call, the duration of the call, to whomthe call was made to, from whom the call was made, with respect to aphone conversation taken place via the mobile device, (3) the web pagefetched from a browser on the mobile device, (4) the results of a WAPenabled pull of data.

Select communication events 1724 are displayed on the viewing screen1726. In FIG. 15 a, for example, the status of each select communicationevent is represented on the viewing screen 1726 using a single letter,as well as using bold type to emphasize communication events which havenot yet been attended to by the user. Conversely, italic type is used torepresent communication events that have been attended to by the user,although attended events may also be omitted from the display to furtheremphasize the select communication events. Furthermore, the type of eachselect communication event is represented on the viewing screen 1726 inFIG. 15 a, for example, by an icon 1727 (alternatively by a short wordor acronym such as email, SMS, WAP, call). Furthermore, the data of eachselect communication event is represented on the viewing screen 1726 inFIG. 15 a, for example, in the form of a short textual representation.Further still, the select communication events are represented on theviewing screen 1726 in FIG. 15 a, for example, in the form of a table.It should be understood, however, that the user interface 1720 is notlimited to use with those representations, or those illustrated types ofcommunication events. Rather, the user interface 1720 may be used withany form of communication event, such as e-mail communication events,SMS communication events, web communication events, WAP communicationevents, as well as other data, voice, and video communication events. Itis to be understood that the user of the mobile device 100 may scrollthrough the listing of the select communication events and determinewhich of these events he desires to act further on by requesting menuselection user interface as illustrated in FIG. 2 b. The user would thenchoose one of the action items presented in the menu selection userinterface to retrieve more information about the selected communicationevent or act on the selected communication event.

In addition to the status 1738, type 1740, and data 1742, thecommunication event software interface module 1734 may also attach sometype of indexing data 1744 to each communication event, such as anordinal value or a time-stamp indicating when the communication eventwas transmitted or received.

In addition to saving and indexing incoming and outgoing communicationevents, the communication event software interface module 1734 filtersthe stored communication events 1736 to select communication eventsrelating to pre-set criteria. FIG. 15 b illustrates another embodimentof how select communication events 1724 are displayed on the viewingscreen 1726. By way of example, the latest three communication eventswill be briefly described. The first is an e-mail message received atthe mobile device and sent from Person Y. The email icon 1727 is shownand acronym RCV is used to indicate it was received versus sent from themobile. The time 08:00a indicates the time it was received at the mobiledevice. The sender's name appears next to the subject line of the emailmessage. The next communication event is an incoming telephone voicecall received at the mobile device. In this instance, a call icon 1727appears. The acronym RCV again appears, the time the call was received,the caller name (alternatively or additionally, the telephone number ofthe caller), and duration of the call all appear. The next communicationevent is an outgoing telephone voice call. In this instance, the callicon 1727 is indicative of the fact that a memo (or notes) made by theuser of the mobile device is also available should the user open thiscommunication event to read more information.

As one skilled in the art of user interfaces can appreciate there wouldbe many ways to present the unified user interface (UUI). One goal ofthis UUI is for the user to review important events at any time theylike. It would also be a central location the user would go when themobile device 100 notifies them that something has been received. Thelists shown in FIGS. 15 a and 15 b are examples, but many other UIrepresentations could be used. Preferably, the information to bepresented includes, date and time of the event, type of event, directionof the event, i.e. Sent or Received, and a summary of information thatmight help with a quick glance at the event. In this example we havesummarized all the events by day, and a leading icon is used to indicatethe type of event, shown as an envelop for e-mail events and a phone forphone events. This field is then followed by a direction indicator,either Snt or Rcv and a time for when the event took place. Finallythere is summary information like the person that sent the message ormade the phone call, and the subject line, or call duration. It is clearto one skilled in the art that this summary information could contain arange of other information contained within the event not shown in thisFigure.

The above-described embodiments of the present invention are intended tobe examples only. Alterations, modifications and variations may beeffected to the particular embodiments by those of skill in the artwithout departing from the scope of the invention, which is definedsolely by the claims appended hereto.

1. A mobile electronic communication device, comprising: a communicationsubsystem for receiving from a communication network a plurality ofdifferent types of received communication events comprising an e-mailmessage and an instant message having data; a memory for storing thedata of the plurality of different types of received communicationevents; a display; a processor a transmitter for wirelessly transmittinga plurality of different types of transmitted communication events; anda communication event interface executable by the processor, thecommunication event interface when executed causing the display todisplay a listing having truncated textual representations of the dataof the plurality of different types of received communication events andto display the listing further having truncated textual representationsof data of the plurality of different types of transmitted communicationevents.
 2. The mobile electronic communication device of claim 1,wherein the truncated textual representations comprise truncated subjectlines.
 3. The mobile electronic communication device of claim 1, whereinthe truncated textual representations comprise truncated message bodies.4. The mobile electronic communication device of claim 1, wherein thetruncated textual representations comprise an indication of truncation.5. The mobile electronic communication device of claim 4, wherein theindication of truncation comprises an ellipsis.
 6. The mobile electroniccommunication device of claim 1, wherein the listing further comprisesdifferent icons indicative of the different types of the receivedcommunication events.
 7. The mobile electronic communication device ofclaim 1, wherein the listing further comprises indications of statusesof the received communication events.
 8. The mobile electroniccommunication device of claim 1, wherein the listing further comprisestime-stamps indicating when the received communication events werereceived.
 9. The mobile electronic communication device of claim 1,wherein the listing further comprises names of senders of the receivedcommunication events.
 10. The mobile electronic communication device ofclaim 1, wherein the plurality of different types of receivedcommunication events comprises different types of messages.
 11. Themobile electronic communication device of claim 1, wherein the datacomprises a message body of the e-mail message.
 12. The mobileelectronic communication device of claim 1, wherein the data comprises amessage body of the instant message.
 13. The mobile electroniccommunication device of claim 1, wherein the data comprises a subjectline of the e-mail message.
 14. The mobile electronic communicationdevice of claim 1, wherein the plurality of different types of receivedcommunication events further comprises a short message service (SMS)message.
 15. The mobile electronic communication device of claim 14,wherein the data further comprises a message body of the SMS message.16. The mobile electronic communication device of claim 1, wherein thedata comprises header information.
 17. The mobile electroniccommunication device of claim 1, wherein wirelessly receiving compriseswirelessly receiving at least one signal comprising data packets.
 18. Amethod for a mobile electronic communication device, the methodcomprising: wirelessly receiving from a communication network aplurality of different types of received communication events havingdata; storing the data of the plurality of different types of receivedcommunication events; wirelessly transmitting a plurality of differenttypes of transmitted communication events; and displaying a listinghaving truncated textual representations of the data of the plurality ofdifferent types of received communication events and truncated textualrepresentations of data of the plurality of different types oftransmitted communication events.
 19. The method of claim 18, whereinthe plurality of different types of received communication eventscomprises different types of messages.
 20. The method of claim 19,wherein the different types comprise two or more of e-mail messages,instant messages, and short message service (SMS) messages.
 21. Themethod of claim 18, wherein the truncated textual representationscomprise an indication of truncation.
 22. The method of claim 18,wherein the listing further comprises different icons indicative of thedifferent types of the received communication events.
 23. A mobileelectronic communication device comprising a processor and a display,the mobile electronic communication device configured to display aplurality of truncated textual representations of data of a plurality ofdifferent types of communication events received by the mobileelectronic communication device from a communication network and todisplay a plurality of truncated textual representations of data of aplurality of different types of communication events sent by the mobileelectronic communication device.
 24. The mobile electronic communicationdevice of claim 23, wherein the truncated textual representationscomprise truncated subject lines of e-mail messages.
 25. The mobileelectronic communication device of claim 23, wherein the truncatedtextual representations comprise truncated message bodies of e-mailmessages.
 26. The mobile electronic communication device of claim 23further configured to display different icons indicative of thedifferent types of communication events received by the mobileelectronic communication device.
 27. The mobile electronic communicationdevice of claim 23 further configured to display statuses of thecommunication events received by the mobile electronic communicationdevice.
 28. The mobile electronic communication device of claim 23further configured to display time-stamps indicating when thecommunication events received by the mobile electronic communicationdevice were received.
 29. The mobile electronic communication device ofclaim 23 further configured to display names of senders of thecommunication events received by the mobile electronic communicationdevice.
 30. The mobile electronic communication device of claim 23,wherein the plurality of different types of communication eventsreceived by the mobile electronic communication device comprises atleast two of an e-mail message, an instant message, and a short messageservice (SMS) message.